<?php
/**
 * <https://y.st./>
 * Copyright © 2017 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Don&apos;t assume',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<section id="general">
	<h2>General news</h2>
	<p>
		Yesterday as I was heading out the door to go to work, I found my bike&apos;s tire deflated.
		Reinflating it, I found it held air long enough to get to work, though it lost its firmness by the time I clocked off.
		I considered just travelling by foot for a while until I had tome to get a new inner tube, but I have finals coming up in Eugene.
		I need my bike in working order.
		Before work today, I headed to the store to replace the tube.
		Unfortunately, the only brand of inner tube the store sold was Bell.
		Also unfortunately, I don&apos;t have time to search for a different tube.
		When I have time, I should check the bike store to see if they have something else I can get and keep at home for next time I need a replacement.
	</p>
	<p>
		I&apos;m not sure where I put my wrench though.
		Last I remember, it was on the shelf in my living room.
		Most likely, it got misplaced when I was clearing out the living room so my mother could store her stuff there.
		She still hasn&apos;t put anything in there, either.
		So I&apos;m stuck without a living room, but no one is even getting anything out of that.
		It&apos;s rather frustrating.
	</p>
	<p>
		As I was working drive-through, I overheard a parent explaining to their child that they shouldn&apos;t assume someone&apos;s gender without asking them.
		As someone that always has people misgender me, I appreciate parents making an effort to help with that.
	</p>
</section>
<section id="university">
	<h2>University life</h2>
	<p>
		I finished my discussion assignment for the week:
	</p>
	<blockquote>
		<p>
			&quot;Responsive design&quot; is a buzzword referring to Web design that causes pages to adapt to fit the screen they&apos;re viewed on (Lawson, 2012).
			Until this week, I wasn&apos;t aware of what the term meant, but the concept is something I&apos;ve been supporting for years.
			If you&apos;ve read some of my past discussion posts in this course, you may have noticed that I mentioned that a webpage can rearrange its content to be displayed better for different screen sizes, and that this is a much better option than sending users to different pages based on arbitrary criteria such as <code>User-Agent</code> headers.
			This concept of pages that display differently depending on the screen size or device, while the server is still sending the same exact page to all devices, is exactly what responsive design is.
			It&apos;s made possible by $a[CSS], which can either take the screen size into account (I&apos;ve seen it done, though I&apos;m not sure how) or can instruct the client to download the appropriate $a[CSS] based on what kind of device the client sees itself as.
			There are two very important details here.
			First, <strong>*all*</strong> of the same <strong>*content*</strong> is sent to <strong>*everyone*</strong>.
			If you&apos;re handicapping your users by sending a lesser version of a page, that&apos;s <strong>*not*</strong> responsive design.
			If you&apos;re sending a separate page that you <strong>*think*</strong> is equal in value to some user, that is <strong>*not*</strong> responsive design, and you&apos;re wrong that it&apos;s equal, because separate is <strong>*never*</strong> equal.
			Second, the <strong>*server*</strong> is making zero discriminatory efforts here.
			The client might end up with different $a[CSS], but the server isn&apos;t choosing which $a[CSS] to send.
			The <strong>*client*</strong> is choosing which $a[CSS] to download based on what kind of device it identifies as.
			In this way, you give up trying to cram your own choices down the user&apos;s throat and let them (and their client software) decide.
			It&apos;s also worth noting that $a[CSS] is style, not content, so it&apos;s okay for different users to use different $a[CSS].
		</p>
		<p>
			Dennis Kardys (Kardys, 2012) makes a good point as well.
			Even if you&apos;re too hard-headed to see that mobile users shouldn&apos;t be served a dumbed-down version of your website, where do you draw the line?
			Screens come in a multitude of sizes.
			At what arbitrary point do you say that just one pixel less in screen width means the user should be not allowed to see the full content of the website?
			Attempting to pinpoint this line really drives home exactly how <strong>*arbitrary*</strong> such a line is.
			A screen is a screen, a user is a user, and we should be making our content manageable for all users.
			It&apos;s also worth noting that when you serve two (or more) versions of a page, you&apos;re having to <strong>*maintain*</strong> both (or all) versions.
			Sure, it may take more time to initially test the single, responsive, clean design, but you&apos;ll save yourself a lot of upkeep in the future.
		</p>
		<p>
			Usually, when people refer to the &quot;mobile Web&quot;, they&apos;re referring to a subset of the Web geared toward mobile devices.
			They&apos;re referring to treating mobile device users as second-class citizens and not allowing them to access the main website.
			And they&apos;re often referring to forcibly redirecting users to a given version of a website after attempting to guess what device they use based on their <code>User-Agent</code> header.
			If we use the term &quot;mobile Web&quot; to refer to these things, the only thing important about the mobile Web is that it&apos;s a backwards idea that we need to get out of our heads.
			Now.
			We must never engage in such poor practices.
		</p>
		<p>
			On the other hand, if we use the term &quot;mobile Web&quot; to refer to the making of our main websites accessible to mobile devices, we&apos;re instead left with a very powerful tool for not only making our websites better for mobile users, but for making them better for desktop users as well.
			Mobile users and desktop users often want the same thing: a website without clutter and that gets right to the point.
			Limitations of mobile devices turns these desires into something closer to needs, but if we clean up our websites to work well on mobile devices without stripping away  vital functionality, we&apos;ll actually improve the Web for all users.
		</p>
		<div class="APA_references">
			<h3>References:</h3>
			<p>
				Kardys, D. (2012, June 7). How To Sketch A New Mobile Web – Smashing Magazine. Retrieved from <a href="https://www.smashingmagazine.com/2012/06/sketching-a-new-mobile-web/"><code>https://www.smashingmagazine.com/2012/06/sketching-a-new-mobile-web/</code></a>
			</p>
			<p>
				Lawson, B. (2012, April 19). Why We Shouldn&apos;t Make Separate Mobile Websites – Smashing Magazine. Retrieved from <a href="https://www.smashingmagazine.com/2012/04/why-we-shouldnt-make-separate-mobile-websites/"><code>https://www.smashingmagazine.com/2012/04/why-we-shouldnt-make-separate-mobile-websites/</code></a>
			</p>
		</div>
	</blockquote>
	<blockquote>
		<p>
			The viewport doesn&apos;t only change with the screen size, but also with the window size.
			On a mobile device, the Web browser (as well as any other application) will usually take up the entire screen.
			This isn&apos;t the case with desktop and laptop machines though.
			Many users maximise their Web browser window, or even put it in full screen mode (two separate large sizes, with maximised windows being slightly smaller than full screen mode), but not everyone does that.
			A user might have their Web browser open to half the size of their monitor, or two thirds the size, or any other size they choose.
			In other words, the viewport can have any of a range of sizes depending on the monitor size.
			This is another reason why responsive design is so important.
			Not only should we not assume a user&apos;s screen size, we also shouldn&apos;t assume they have their Web browser window maximised.
		</p>
	</blockquote>
	<blockquote>
		<p>
			I knew about using a <code>&lt;meta/&gt;</code> element to get pages to display correctly.
			For some bizarre reason, without that element, Web pages often appear zoomed way out on mobile devices, and yet the paragraph text is all scrunched together so that if you zoom in manually, everything looks fine.
			Setting the viewport to 100% in the <code>&lt;meta/&gt;</code> tag fixes that.
			Your <code>max-width</code> on images, alternate images based on viewport size, and <code>vw</code> unit are all new tricks to me though.
			Those look like they could be fantastic for making websites that adapt gracefully to different screen sizes.
			I&apos;ll have to try them out when I get a chance.
		</p>
	</blockquote>
	<blockquote>
		<p>
			I wouldn&apos;t say that mobile devices are easier to use than desktop and laptop machines by any means.
			In fact, I&apos;d say just the opposite.
			Mobile devices are severely limited in both functionality and interface.
			Desktops and laptops will probably be easier to use for the next several decades, at least.
			That said, mobile devices are often <strong>*more convenient*</strong> to use, so they do often see more use than bulkier, more-capable machines.
		</p>
	</blockquote>
</section>
END
);
